Method and software for enabling n-way collaborative work over a network of computers

ABSTRACT

Method, software, and system for efficiently enabling n-way collaborative work using common software over a network of computers. In a preferred embodiment of the invention, each participant in a collaborative session starts up a common software application, which includes a collaboration component. This collaboration component is used to establish a common session that includes all interested parties. The collaboration component replicates operations performed on any one instance of said application to all other instances participating in the same session, so the effect is as if all members of the session were sharing a single instance of the application on a single computer. In one aspect, the collaboration component also supports broadcast of audio and video over a computer network, to enable session participants to see and/or hear each other, and further includes other features that support collaborative work.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/201,355, filed Aug. 29, 2008, entitled “METHOD AND SOFTWARE FORENABLING N-WAY COLLABORATIVE WORK OVER A NETWORK OF COMPUTERS,” thecontent of which is hereby incorporated by reference in its entirety.

BACKGROUND

Collaborative work over the Internet, as an alternative to actualface-to-face meetings, has been growing in popularity. Discussions andlectures can be held while individual participants are in geographicallydistant locations.

A major requirement for efficient collaborative work of this kind is theability to view a common document—whether a text document, overheads fora lecture, or a multimedia presentation. This preferably includes theability to allow all participants to examine the document, the abilityto direct everyone's attention to a specific item or page of thedocument, and the ability to add annotations that are visible (andperhaps modifiable) by all participants in the meeting. Furtherdistinctions are possible: (i) one can distinguish between “synchronouscollaboration” and “asynchronous collaboration”; and (ii) one candistinguish between “one-way collaboration” and “n-way” collaboration.In “synchronous collaboration,” all collaboration activities occuronline, and participants interact in real-time. In “asynchronouscollaboration,” collaboration activities can occur at different timesfor each participant. In “one-way collaboration,” only one of theparticipants can manipulate the shared document—the others are just“along for the ride” (i.e., able only to view). In “n-waycollaboration,” any of the participants can perform operations that arethen visible also to all fellow participants.

Two approaches are commonly used to provide these abilities. The firstapproach is to use a universal document representation scheme andinstall on the workstations of all participants an application able tomanipulate documents. In some cases, the application has been enhancedto support collaborative work. This is the more common approach. HTML istypically chosen as the representation scheme, and a web browser (e.g.,Netscape or Internet Explorer) is the common application. But such ascheme has disadvantages: web browsers do not “abstract away” fromworkstation-specific issues, such as screen size and resolution. As aresult, products may be unable, for example, to place a highlighter inthe same spot in the document as viewed by all participants in asession, causing obvious confusion.

The other common approach—known as “application sharing”—assumes thatthere is not one application common to all participants. To solve thatproblem, a single workstation is chosen to run the application needed tomanipulate the document. The user at that workstation manipulates thedocument directly. Each of the other users is presented with adynamically-updated snapshot of the screen window displayed by theapplication on the workstation. The remote users are able to manipulatethe joint document through the replication of low-level events (such asmouse motion and keyboard operation) from the remote user's computers(where the snapshot is shown) to the workstation (where the applicationactually runs). There are at least two shortcomings to this approach:(a) it can be expensive, in terms of bandwidth required to replicate thesnapshot across all remote computers; and (b) it can create asubstantial security risk, since the technology used to replicatelow-level events can be used to give a remote user control over theworkstation where the application runs.

There is thus a need for an approach that provides the better featuresassociated with each of the above approaches, without theircorresponding drawbacks.

Another requirement for efficient collaboration is the ability toaudibly and/or visually interact with other participants in a session.Many of the collaborative applications presently available rely on ateleconference over regular telephone lines to provide this component ofthe meeting experience. Such an approach can be quite cumbersome, sinceit may require that the participants manage computers as well astelephones. Often only voices, and not visual images, are distributed.Some collaborative applications provide for the delivery of audio andvideo information over the same computer network used for thecollaborative work. This leads to a much more “real” experience for theparticipants.

However, there remains a need for a solution that provides for scalabledelivery of audio/video information, capable of adapting the a/v streamsto the bandwidth available to each participant.

SUMMARY

One goal of the present invention is to provide a system, method, andsoftware for synchronous collaborative work over a collection ofcomputer workstations networked together that support a powerful,flexible, universal, and scalable model of n-way collaborative work. Ina preferred embodiment, Acrobat's PDF standard is used for documentrepresentation, since it is both ubiquitous and more powerful than HTML.The PDF document standard includes support for a variety of documentcontent types, including multimedia parts, along with a variety ofannotation types. In the same preferred embodiment, the Adobe Acrobatapplications (“Acrobat” and “Acrobat Reader”) are used as the commonapplication platform. These applications are enhanced with a plug-inmodule that is particularly suited to support synchronous collaborativework. The preferred plug-in module ties into each application's internalevent processing engine, then propagates any events that occur in anyone instance of the application that has joined a common session to allother participants in the same session, thus providing for a sharedexperience. The plug-in module preferably also provides audio/videoservices, to enable session participants to see and/or hear each other,when practical.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 depicts a computer network used in a preferred embodiment of theinvention.

FIG. 2 depicts software architecture used in a preferred embodiment.

FIG. 3 depicts a user interface directed to an “owner” of acollaborative session using a preferred embodiment.

FIG. 4 depicts a user interface directed to a participant in acollaborative session using a preferred embodiment.

FIG. 5 illustrates sending of events within a preferred application.

FIG. 6 illustrates a first preferred approach to receiving events withina preferred application.

FIG. 7 illustrates a second preferred approach to receiving eventswithin a preferred application.

FIG. 8 illustrates a preferred method for providing a consistentexperience to all participants in a collaboration session.

FIG. 9 is a UML model depicting preferred classes used for interactionwith a preferred application.

FIG. 10 is a UML model depicting preferred classes used for transmittingevents across preferred plug-ins.

FIG. 11 is a UML model depicting preferred core classes used in apreferred plug-in.

DETAILED DESCRIPTION

A preferred embodiment of the present invention enables collaborativework on a common application and minimizes overhead without sacrificingsecurity of workstations used to participate in a collaborative session.A preferred method comprises installing a collaboration module (plug-in120—see FIG. 1) within a common application 130. The plug-in 120preferably interfaces with event processing mechanisms of theapplication 130 in at least two ways: (1) by tracking what operationseach participant in a session executes on the participant's instance ofthe application 130, then propagating those same operations across acomputer network to other instances of the application 130 participatingin that session; and (2) by receiving event notifications (eitherdirectly or indirectly, from a session manager 110 who relays suchnotifications) from other participants' plug-ins during the session, andreplicating those notifications as operations on the local instance ofthe application 130.

The method preferably comprises algorithms to resolve potential problemsin synchronizing concurrent, conflicting operations. Typically,applications providing the ability for a plug-in 120 to interface withtheir own internal event processing are of two types: (1) those thatsupport a “push” mode, in which delivery of events from the plug-in 120to the application 130 occurs when the plug-in 120 receives the event;and (2) those that require a “pull” mode, in which delivery of events tothe application 130 occurs at times the application designates. Apreferred plug-in 120 can operate in either environment. When anapplication 130 requires “pull” delivery of events, the plug-in 120queues events received from the session until the application 130 isready to handle them. But when “push” delivery of events to theapplication 130 is possible, events do not need to be queued. FIG. 2illustrates this architecture. Since communications protocols of apreferred embodiment of the invention propagate application-levelevents, those protocols are more efficient than lower-level,platform-specific events, in that network overhead is minimized.

In one embodiment, preferred plug-ins 120 communicate with each othervia a central session manager 110 that acts as a relay station, in whatis commonly known as a “star network” (see FIG. 1). This guarantees thateach of the session participants only needs to pay the network overheadassociated with their own participation in the session; only the sessionmanager 110 needs to pay overhead proportional to the “size” (number ofparticipants) in a session. Such a session manager 110 can be providedas a service by a service provider (such as an ISP), or can be suppliedby one of the participants in the session. That is, in one embodiment,the session manager 110 is incorporated with the plug-in 120 used by oneof the participants.

The security of workstations participating in a session is guaranteed attwo levels: (1) communications across instances of the application 130in a common session are limited to events meaningful only within thatapplication—any other resources present on any participating workstationare ignored; and (2) a preferred plug-in 120 propagates no events thatcould have an effect outside the application.

Privacy of a session also is guaranteed at two levels: (1) in order toreceive notifications of events from other participants' workstations, aparticipant must join a session, and join protocols can preventunauthorized parties from joining in; and (2) communications over anetwork that links workstations in a session can be encrypted, toprevent eavesdropping.

To illustrate in detail how a preferred embodiment of the method works,a sample implementation is described below, wherein Adobe Acrobat isused as the common application 130.

Assume for the purposes of this example that a number of session manager110 servers are available somewhere on the Internet, and assume thatthere is also a session server directory available through some website. However, the prior existence of a session manager server is notrequired. A creator of a new session preferably can configure his or herown instance of the application 130 to act as a session manager 110 fora particular session.

To begin a collaborative session, the participant who will “manage” thesession (the “owner”) preferably first starts up an instance of theapplication 130 to be run, so that the owner can then create a sessionfor everyone else to join. After the owner starts the application 130,he enters configuration data for himself into a form 310 (see FIG. 3).The owner's configuration data preferably includes informationsufficient to identify him within the session, along with configurationdata to be used in case a direct connection from this application 130 toothers on the Internet is not possible (the address and port number usedfor a proxy server to act as a relay for all communications, forexample). Other participants in the session to be created (“users”) needto enter similar information into a form 410 (see FIG. 4).

When the application 130 starts up, it also starts up an instance of apreferred plug-in 120 that executes within the application 130. Onstartup, the plug-in 120 preferably registers with the application 130the plug-in's interest in receiving notification of all interestingapplication-level events detected by the application 130. These eventscorrespond to all operations performed by a user of that application130. Opening and closing files, navigating within a file, and addingannotations to a file are examples of application-level events detectedby Adobe's Acrobat. Acrobat preferably notifies the plug-in 120 of theoccurrence of any of these events, as each happens. Code allowed toregister as an event handler with Acrobat must be “native” C/C++ code.Since the core 510 (se FIG. 5) of a preferred plug-in 120 is written inJava, the interface between the Acrobat application 130 and the Javaplug-in comprises two layers: (1) a set of C++ functions 530individually written to register as handlers with each of the eventtypes defined by Acrobat; and (2) a Java function 520 corresponding toeach C++ function, to relay the handling of these events to the core ofthe Java plug-in 120. The processing of each event within a preferredplug-in 120 could be time-consuming; therefore, to hide any resultingdelay from a user of the application 130, the plug-in 120 preferablyqueues up (in queue 510) events received from its own application 130,while the application 130 processes the next user request. FIG. 5illustrates this architecture.

The instances of the preferred plug-in 120 that are part of a commonsession preferably do not interact with each other directly. Instead, tominimize network overhead paid by any one participant of the session,each instance of the plug-in 120 communicates with a central sessionmanager 110. This session manager 110 acts as a distribution point andrelay station, receiving each event notification from each plug-in 120and re-transmitting it to all other plug-ins that participate in thesame session. To minimize processing delay “perceived” by a sendingplug-in 120, the session manager 110 also queues up event notificationsit receives for processing. The plug-in 120 that transmits an event tothe session manager 110 preferably receives an acknowledgmentimmediately, and continues execution while the session manager 110 goeson to retransmit the received event to every other plug-in 120 in thatsession.

Each plug-in 120 also receives event notifications from the centralsession manager 110. These event notifications are used to replicate onthe application 130 associated with the receiving plug-in 120 theactions performed by the user on the application 130 associated with thesending plug-in 120. Again, to minimize the delay associated with theprocessing of the event on the receiving side, the receiving plug-in 120queues up event notifications it receives and acknowledges themimmediately to the central session manager 110. This enables the sessionmanager 110 to continue processing while the receiving plug-in 120processes the event it received.

In one embodiment, the application 130 associated with the plug-in 120supports execution of commands corresponding to “pushed” eventnotifications received. In this case, the preferred plug-in 120 canproceed to invoke the commands associated with each event as itretrieves them from the queue 510. FIG. 6 illustrates this approach.However, it is also possible that the application 130 would not supportsuch execution, but would rather require that commands be executed onlywhen the application 130 thought it appropriate. In this second case, apreferred plug-in 120 keeps incoming event notifications in the arrivalqueue 510, and waits for the application 130 to request the delivery ofan event. Such a request would entail the execution of the commandassociated with the event, but under the application's control and atits convenience. Adobe's Acrobat is an example of this second type ofapplication. FIG. 7 illustrates this second approach.

One problem addressed by a preferred embodiment of the invention isrelated to the sequence of operations that the users of the individualinstances of the application 130 in the session will observe theirinstance of the application 130 execute, taking into account theconcurrent execution of operations by each of the users that need to bereplicated across the session. If no special care were taken, each ofthe individual users could receive the sequence of operations in adifferent order, potentially depriving them of the desired commonexperience. To address this potential problem, a preferred embodimentcomprises a method to sequence operations broadcast to all participantsin a session that ensures that they do share a common experience.

The preferred method comprises the following steps (see FIG. 8). At step810 session manager 110 receives an event notification with the sequencenumber “reqSeqNum” of the last event received by the sending plug-in. Atstep 820 the session manager compares the received sequence numberreqSeqNum to the number “lastSeqNum” of the last event broadcast bysession manager 110. If the two numbers are equal, then at step 830session manager 110 assigns a new sequence number to the received eventnotification, and save that number as lastSeqNum. At step 840 sessionmanager 110 designates the participant plug-in from which it receivedthe event notification as “lastSender.” At step 850 session manager 110broadcasts the received event notification to all participants (otherthan lastSender) and then waits to receive the next event notificationat step 810.

However, if at step 820 reqSeqNum does not equal lastSeqNum, then atstep 860 session manager 110 compares the sender of the notification tolastSender. If the two are the same, session manager 110 proceeds tostep 830, for reasons discussed below. If the two are not the same, thereceived event notification is ignored, and session manager 110 waist toreceive the next event notification at step 810.

Session-based event sequence numbers are assigned to each of the eventsthat arrive at the session manager 110, before they are relayed to allthe participants in the session. When a participant's plug-in 120 sendsan event notification to the session manager 110, the notificationcomprises an event sequence number for the last event the plug-in 120received. The session manager 110 preferably ignores event notificationsfrom participants when the event sequence number that accompanies therequest is lower than the last sequence number assigned. Such a scenariowould typically only occur if the participant had yet to process anevent that had already been sent out. In such a case, ignoring thenotification will have the effect of giving that participant a chance to“catch up.” The session manager 110 preferably may only accept the eventnotification, even if the event sequence number is not the last oneused, when the participant plug-in 120 sending the notification was alsothe participant plug-in 120 that sent the notification corresponding tothe last sequence number issued. In that case, that plug-in 120 may nothave received its own event notification (there is often no need for aplug-in 120 to have received notification of its own events).

FIGS. 9 through 11 illustrate in more detail a sample implementation ofthe preferred method. FIG. 9 depicts a preferred UML model for coderesponsible for actual interaction between the application 130 and theplug-in 120. Type “AcrobatProxy” 910 is the Java description for“native” C++ code actually registered with the Acrobat event processingengine. Type “Acrobat” 920 is Java code invoked by native functions inorder to hand off an event notification from the application 130 to itsplug-in 120.

FIG. 10 depicts a preferred UML model for code responsible forcommunications across plug-ins. Type “Session” 1010 provides Java codeused remotely by a sending plug-in 120 to communicate to a sessionmanager 110 that a new event took place. Type “SessionParticipant” 1020describes receiving plug-in 120 s that receive event notifications froma session manager 110.

FIG. 11 depicts a preferred UML model for basic structure of a preferredplug-in 120. Type “Acrobat” 1110 is a description of Java code within apreferred plug-in 120 that is called to handle locally an eventnotification received from the application 130, or to relay back to theapplication 130 a request to execute an operation. Type “Session” 1120is an object within the session manager 110 that plug-ins communicateevents to. Type “SessionParticipant” 1130 is a description for codewithin a preferred plug-in 120 that receives notifications from asession manager 110 and passes them on to code described by the Acrobatclass for processing.

While the invention has been described with respect to the preferredembodiments, those skilled in the art will recognize that numerousvariations and modifications may be made without departing from thescope of the invention. Accordingly, it should be clearly understoodthat the embodiments described above are not intended as restrictions onthe scope of the invention, which is limited only by the followingclaims.

1. A method for collaboration over a computer network, comprising:intercepting data regarding one or more application level events thatoccur within a first instance of a stand-alone application operable tocreate and edit to documents in response to user actions, and whereinthe one or more application level events reflect user actions thatresult in changes to a native document file generated by the firstinstance of stand-alone application; transmitting data comprising thenative document file and the data regarding one or more applicationlevel events over the computer network, automatically and in real time,to a second instance of the stand-alone application; and causing thesecond instance of the stand-alone application: to display a local copyof a document corresponding to a local copy of the native document file,to receive and use the data comprising data regarding one or moreapplication level events to replicate the events that occurred withinthe first instance, to mirror the user actions performed in the firstinstance without user intervention by performing an equivalent action onthe local copy of the native document file and thereby makecorresponding changes to the local copy of the native document file, andto display the changes to the local copy of the document, wherein noevents that have an effect outside the stand-alone application arepropagated to provide security of the collaboration.
 2. A method as inclaim 1, wherein the one or more application level events include addingannotations to the document in response to the user actions, and whereinthe changes displayed to the local copy of the document include theadded annotations.
 3. A method as in claim 1, wherein the stand-aloneapplication is Adobe Acrobat.
 4. A method as in claim 1, wherein thesecond instance of the stand-alone application is further configured toqueue received event notifications.
 5. A method as in claim 4, whereinthe second instance of the stand-alone application controls retrieval ofthe queued event notifications from multiple participants and resolvesconflicts between the events.
 6. A method as in claim 1, wherein thedata regarding one or more application level events is transmitted tothe second instance via a session manager, and in which conflictresolution between events from different sources is performed by thesession manager.
 7. A method of claim 1, wherein the stand-aloneapplication comprises a document viewer viewing a first copy of a nativedocument file generated by the first instance of the stand-aloneapplication.
 8. A method as in claim 7, wherein the application is AdobeAcrobat or Adobe Reader.
 9. A method as in claim 1, wherein theapplication level events comprise one or more text changing events. 10.A method as in claim 1, further comprising saving the local copy of thenative document file with changes including the added annotations madeby the replicated events incorporated therein.
 11. A method as in claim1, wherein the second instance of the stand-alone application detectsconflicts between the application level events and resolves detectedconflicts between the application level events without requiring userintervention.
 12. A method as in claim 1, wherein a session managerdetects conflicts between the application level events and resolves thedetected conflicts using sequence numbers assigned to the applicationlevel events and without requiring user intervention.
 13. A computerreadable storage medium storing software for collaboration over acomputer network, comprising: a software plug-in operable to interceptdata regarding application level events that occur within a firstinstance of a stand-alone application operable to create and editdocuments in response to user actions, and to which the first instanceof the software plug-in has been plugged in and wherein the one or moreapplication level events reflect user actions that result in changes toa native document file generated by the first instance of stand-aloneapplication are delivered to the plug-in, wherein a sequence number isassigned to each of the one or more application level events to resolveany conflicts between the one or more application level events; whereinthe software plug-in is further operable to receive data regarding oneor more application level events that occur within a second instance ofthe stand-alone application and are transmitted over the computernetwork from a second instance of the plug-in plugged into the secondinstance of the stand-alone application, wherein the instances ofstand-alone application are separate instances; wherein the firstinstance of the software plug-in is further operable to use the receiveddata regarding one or more application level events to replicate theevents that occurred within the second instance of the stand-aloneapplication, using the first instance of the stand-alone application tomirror the user actions performed on the second instance by performingan equivalent action including on a local copy of the native documentfile, and to display the changes to the local document corresponding tothe native document file, automatically, in real time, and without userintervention, and wherein communications over the computer network thatlinks workstations in a session are encrypted to preserve privacy of asession.
 14. A computer readable storage medium storing software as inclaim 13, wherein the stand-alone application is Adobe Acrobat.
 15. Acomputer readable storage medium storing software as in claim 13,wherein the data regarding one or more application level events istransmitted by the second instance via a session manager.
 16. A computerreadable storage medium storing software as in claim 13, wherein thefirst instance of the stand-alone application detects conflicts betweenthe application level events and resolves detected conflicts between theapplication level events without requiring user intervention
 17. Acomputer readable storage medium storing software as in claim 13,wherein the session manager detects conflicts between the applicationlevel events and resolves the detected conflicts using a sequencenumbers assigned to the application level events and without requiringuser intervention.
 18. A method for collaboration over a computernetwork, comprising: intercepting data regarding one or more applicationlevel events that occur within a first instance of a stand-aloneapplication operable to create and edit documents in response to useractions, and wherein the one or more application level events reflectuser actions that result in changes to a native document file generatedby the first instance of stand-alone application wherein a sequencenumber is assigned to each of the one or more application level eventsto resolve any conflicts between the one or more application levelevents; transmitting data comprising the native document file and thedata regarding one or more application level events over the computernetwork, automatically and in real time, to a one or more otherinstances of the stand-alone application, wherein the instances ofstand-alone application are separate instances running only onworkstations operated by users; receiving data regarding one or moreapplication level events that reflect user actions that result inchanges to a native document file generated by one or more otherinstances of stand-alone application; and causing the first instance ofthe stand-alone application: to use the received data comprising dataregarding one or more application level events to replicate the eventsthat occurred within the one or more other instances, to mirror the useractions performed in the one or more other instances by performing anequivalent action on the local copy of the native document file andthereby make corresponding changes to the local copy of the nativedocument file, and to display the changes to the local copy of thedocument, wherein no events that have an effect outside the stand-aloneapplication are propagated to provide security of the collaboration. 19.A method as in claim 18, further comprising causing a session manager todetect and resolve conflicts caused by user actions performed in saidone or more other instances.
 20. A method as in claim 18, wherein saidsession manager detects and resolves conflicts using said sequencenumbers assigned to said application level events.